home *** CD-ROM | disk | FTP | other *** search
- Path: news.cc.uic.edu!icarus!dhanle2
- From: dhanle2@icarus.cc.uic.edu (David James Hanley)
- Newsgroups: comp.lang.java,comp.lang.c++,comp.lang.smalltalk
- Subject: Re: Will Java kill C++?
- Date: 16 Apr 1996 18:31:23 GMT
- Organization: University of Illinois at Chicago
- Message-ID: <4l0p1r$1136@piglet.cc.uic.edu>
- References: <31683229.446B9B3D@bbn.com> <DpJs8I.8tn@research.att.com> <AUSTERN.96Apr15104256@isolde.mti.sgi.com>
- NNTP-Posting-Host: icarus.cc.uic.edu
- X-Newsreader: TIN [version 1.2 PL2]
-
- Matt Austern (austern@isolde.mti.sgi.com) wrote:
- : In article <4ks0c8$jte@piglet.cc.uic.edu> dhanle2@icarus.cc.uic.edu (David James Hanley) writes:
-
- : > : Correct about what? That having a name-mangling standard for C++
- : > : would make C++ libraries easier to handle. Sorry, but he's wrong,
- : > : and so are you.
- : >
- : > Nope. You're the one who is wrong here. But seeing as you
- : > replied to my first post about the matter with insults to me, I really
- : > doubt you are interested in serious exploration of the matter.
-
- : I'd think twice before telling Andy flatly that he's wrong about some
- : basic C++ issue.
-
- I'm not calling him wrong on a C++ issue per se. WHere I do think
- he's wrong is in the area of basic logic. Everyone who's familiar with
- compilers knows it's hard to link objects gernerated by different
- compilers. Where I think he's wrong is in the logical(?) progression:
- "It might be hard to do, so let's make it harder." My thought process
- on the matter runs more like: "It's hard to do, so why the hell should
- we make it harder? That's silly."
-
- : There are a whole lot
- : of issues to be resolved if you want to link object files from two
- : compilers: sizes of basic types, direction of stack growth,
- : representation of the number of arguments passed to a subroutine,
- : order in which arguments are passed, mechanism for return types,
- : padding of data structures,
-
- All the above could easily be inhereted from the C abi's for
- the same platform that already exist.
-
- : mechanism for polymorphic function calls,
-
- Probably the only hard one.
-
- : initialization of global data, layout of derived classes (especially
- : in the case of multiple and/or virtual inheritance), representation of
- : object type,
-
- Yes, these would have to be resolved. But none of them are
- particularly hard to do.
-
- : mechanism for linking to dynamic shared libraries,
-
- Already in the C abi..
-
- --
- ------------------------------------------------------------------------------
- David Hanley, |______ Computer Science graduate student.
- dhanley@lac.eecs.uic.edu |\ ___/__ Martial Artist. Biker. Chess Freak
- www_lac.eecs.uic.edu/~dhanley/| \\ / / Libertarian. Atheist. Bisexual.
- My employer barely KNOWS me. | \/BI/ Aspiring novelist.Joyce Kafka Neitzchie
- -----------------------------------\/-----------------------------------------
- I tried to love god in adolecennce, and failed.
- I tried to love a woman, when I had put away childish things, and succeeded.
- Read into that, ye seekers of riddles.
-